-
Notifications
You must be signed in to change notification settings - Fork 1.4k
vm: implement the VM interface for VirtualBox #6437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
a-nogikh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Please also address the ci / build failure and squash the improvement commits into the main one (there's not much value in separate vm: improving the implementation of VirtualBox/vm: enhancing the booting process of VirtualBox commits)
This change adds VirtualBox support to syzkaller. It implements the VM interface for VirtualBox and provides: - full VM lifecycle operations (create, boot, stop, snapshot restore) - serial console hookup and integration with the output merger - proper boot wait logic similar to qemu, using SSH readiness - boot-time crash capture using collected console output
|
Please drop the merge commit, it will fail the CI checks - in this project, we rebase. |
Done |
|
Thanks for contributing these changes! |
This commit introduces support for running syzkaller VMs on VirtualBox. VirtualBox integration enables fuzzing drivers of VirtualBox. The implementation includes VM lifecycle operations such as boot, stop, and snapshot restore functionality.